I was thinking about the opinion that âtaking private communication to public channel increases the amount of information and prevents it from being passed aroundâDM
-
Itâs the systemâs inability to distinguish between [I donât mind seeing it.â and âI want you to see it.â
- Whether the lack of distinction is due to software specifications or the way the work is run is irrelevant.
-
Making information public increases the amount of information that can be âseenâ.
- If the information you âwantâ to see is properly Mentioned., then thatâs all you need to see.
- Failure to distinguish between âmay seeâ and âwant to seeâ information leads to âwant to seeâ information being mixed in with âmay seeâ information.
- âI end up having to watch the whole thing.
-
Responsibility to Mentionâ Culture
- If the sender did not mentions the information he/she wants the receiver to see,
- The sender is responsible for any problems caused by the recipientâs failure to read it.
-
If this culture is established.
- The sender mentions what they want you to see.
- Recipients see preferentially what is mentions.
- â No amount of other âlook goodâ information will be a burden.
-
The burden on the reader and the burden on the writer
- If the information is publicly written and pointed to by permalinks, itâs less work for the writer.
- Just point to it and say, âLook at this.â
- If the information is only in the DM or other places where it cannot be pointed to, there will be copy and paste and other hassles.
- If the information is publicly written and pointed to by permalinks, itâs less work for the writer.
This page is auto-translated from /nishio/ăDMăăăăȘăăŻă«ăăăšæ ć ±éăćąăăăăšăăèȘ€è§Ł using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iâm very happy to spread my thought to non-Japanese readers.